Amplifying radio frequency signals

ABSTRACT

The present disclosure is directed to a system and method for amplifying Radio Frequency (RF) signals. In some implementations, a system includes a first interface, a second interface, secure memory, a user-interface module, a processing module, and am amplification module. The first interface connects to a microSD slot of a mobile host device. The second interface includes an internal antenna for wirelessly communicating with retail terminals. The secure memory stores user credentials and a payment application used to execute financial transactions with the retail terminals. The processing module executes the payment application using the user credentials in response to at least a transaction request received by the RF module and transmits at least one transaction response to the retail terminal based, at least in part, on the executed payment application. The amplification module connected to a lead of the antenna and is configured to amplify at least received RF signals.

CLAIM OF PRIORITY

This application is a continuation-in-part of and claims priority toU.S. patent application Ser. No. 12/272,527, filed Nov. 17, 2008, whichis a continuation-in-part of and claims priority to U.S. patentapplication Ser. No. 12/209,087, filed Sep. 11, 2008, which claimspriority under 35 U.S.C. §119(e) to U.S. Provisional Application No.60/971,813, filed on Sep. 12, 2007, the entire contents of each of theabove-identified cases are hereby incorporated by reference.

TECHNICAL FIELD

This invention relates to network communications and, more particularly,to wirelessly communicating radio frequency signals.

BACKGROUND

Portable electronic devices and tokens have become an integrated part ofthe regular day to day user experience. There is a wide variety ofcommon portable and handheld devices that users have in their possessionincluding communication, business and entertaining devices such as cellphones, music players, digital cameras, smart cards, memory token andvariety of possible combinations of the aforementioned devices andtokens. All of these devices share the commonality that consumer areaccustomed to carrying them with them most of the time and to mostplaces. This is true across the various demographics and age groupsregardless of the level of the sophistication of the consumer, their agegroup, their technical level or background.

These common handheld devices offer options for expandable memory. MicroSecure Digital (microSD) is the popular interface across high-endcellphones while SD and MultiMediaCard (MMC) interfaces are alsoavailable in limited models. MicroSD is the least common denominatorsupported by the majority of these devices and tokens (in terms ofsize). In addition, adaptors are available to convert a MicroSD intoMiniSD, SD, MMC and USB Although most popular MP3 player (iPOD) offer'sa proprietary interface, competing designs do offer standard interfaces.Digital cameras offer mostly SD and MMC while extreme Digital (xD) isanother option. Micro and Mini versions of these interfaces are alsoavailable in several models. Mini-USB is increasingly available acrosscellphones, digital cameras and MP3 players for synchronization withlaptops.

SUMMARY

The present disclosure is directed to a system and method for designingvarious miniature antennas with corresponding capabilities of amplifyingRadio Frequency (RF) signals. In some implementations, a system includesa first interface, a second interface, secure memory, a user-interfacemodule, a processing module, and an amplification module. The firstinterface connects to a microSD slot of a mobile host device. The secondinterface includes an internal antenna for wirelessly communicating withretail terminals. The secure memory stores user credentials and apayment application used to execute transactions with the terminals. Theuser credentials and the payment application are associated with afinancial or transit institution. The user-interface module presents andreceives information through a Graphical User Interface (GUI) of themobile host device. The processing module executes the paymentapplication using the user credentials in response to at least atransaction request received by the RF module and transmits at least onetransaction response to the terminal based, at least in part, on theexecuted payment application. The amplification module connected to alead of the antenna and is configured to amplify at least received RFsignals between the terminal and the system.

The details of one or more embodiments of the invention are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the invention will be apparent from thedescription and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is an example transaction system in accordance with someimplementations of the present disclosure;

FIG. 2 is an example transactions system that transmits transactioninformation through a cellular core network;

FIG. 3 is an example intelligent card of FIG. 1 in accordance with someimplementations of the present disclosure;

FIG. 4 is an example intelligent card that selectively switching anantenna;

FIGS. 5A and 5B illustrate an example of antenna design 1;

FIGS. 6A and 6B illustrate another example of antenna design

FIGS. 7A and 7B illustrate another example of antenna design FIGS. 8A-8Cillustrate another example of antenna design;

FIGS. 9A-9D illustrate another example of antenna design;

FIGS. 10A and 10B illustrate another example of antenna design;

FIGS. 11A and 11B illustrate another example of antenna design;

FIGS. 12A and 12B illustrates yet other examples of an antenna design;and

FIGS. 13A-C are cross-sectional views for a system that passivelyamplifies RF signals;

FIGS. 14A and 14B are cross-sectional views for another system thatpassively amplifies RF signals;

FIGS. 15A and 15B are cross-sectional views for a system that activelyamplifies RF signals;

FIGS. 16A-C illustrate another example of antenna designs; and

FIG. 17 is a cross-sectional view for a system that actively amplifiesRF signals.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a block diagram illustrating an example transaction system 100for wirelessly executing transactions using an intelligent cardindependent of a host device. For example, the system 100 may include amicoSecure Digital (microSD) card that executes transactions withfinancial institutions independent of a host device. Aside from microSD,the system 100 may include other mass storage interfaces that connect anintelligent card to the host device such as, for example, MultiMediaCard(MMC), SD, Universal Serial Bus (USB), Apple iDock, Firewire, and/orothers. An intelligent card is a device configured to insert into orotherwise attach to a host device and access or otherwise executeservices (e.g., transactions) independent of the host device. In someimplementations, the intelligent card may be shaped as a microSD cardincluding, for example, notches, raised portions and/or other features.The system 100 may include an intelligent card that includes a dualinterface. The dual interface may connect the intelligent card to boththe host device through a physical interface (e.g., SD, MMC, USB) andexternal devices through a wireless connection (e.g., NFC, ISO 14443).In some implementations, the intelligent card may include an embeddedsecure chip, Central Processing Unit (CPU) with operating system, localmemory and value added applications accessible by the user through thehost device. A host device may include a cellphone, a smartphone, aPersonal Digital Assistant (PDA), a MPEG-1 Audio Layer 3 (MP3) device, adigital camera, a camcorder, a client, a computer, and/or other devicethat includes a mass memory and/or peripheral interface. In someimplementations, the intelligent card can operate as a master with thehost device being a slave such that the intelligent card controlsoperational aspects of the host device such as a user interface. Theintelligent card in the system 100 may execute one or more of thefollowing: selectively activate an antenna for wireless transactions inresponse to at least an event; verify the host device with a financialinstitution through, for example, a Point Of Sale (POS) using a hostsignature; execute a transaction with a financial institution through,for example, a POS terminal independent of the host device; and/or otherprocesses. By providing an intelligent card, the system 100 maywirelessly execute transactions with financial institutions withouteither requiring additional hardware, software, and/or firmware on thehost device and/or without requiring changes to existing hardware,software, and/or firmware for reader terminals to enable a user towirelessly execute a transaction.

At a high level, the system 100 includes an offline store 102 andclients 104 a and 104 b coupled to financial institutions 106 through anetwork 108. While not illustrated, the system 100 may included severalintermediary parties between the financial institution 106 and thenetwork such as, for example, a transaction acquirer and/or a paymentnetwork host. The offline store 102 includes a mobile device 110 ahaving a transaction card 112 a and a Point of Sale (POS) device 114that executes transactions with customers. The POS device 114 includes aGraphical User Interface (GUI) 109 for presenting information to and/orreceiving information from users. In some implementations, the POS 114may transmit a request to execute a transaction to the transaction card112. The transaction card 112 may transmit authentication information tothe POS 114. The client 104 includes the GUI 115 for presentinginformation associated with the system 100. The client 104 a includes acard reader 116 that interfaces the transaction card 112 c with theclient 104 a. The financial institution 106 may authorize thetransaction based, at least in part, on information transmitted by thetransaction card 112. The mobile device 110 includes a GUI 111 forpresenting information associated with financial transactions.

The offline store 102 is generally at least a portion of an enterprisehaving a physical presence (e.g., building) for operations. For example,the offline store 102 may sell goods and/or services at a physicallocation (e.g., a brick-and-mortar store) directly to customers. In thisexample, the offline store 102 buys or otherwise receives goods (e.g.,produce) from distributors (not illustrated) and then may sell thesegoods to customers, such as users of the mobile device 110. In general,the offline store 102 may offer face-to-face experiences with customersin providing goods and/or services. For example, the offline store 102may be a click-and-mortar store such that a user selects a good orservice using the Internet and purchases and receives the good orservice at the offline store 102. The offline store 102 may provide oneor more of the following services associated with goods: inventory,warehousing, distribution, and/or transportation. As a result, theoffline store 102 may not immediately distribute goods received fromdistributors. The offline store 102 may include a single retailfacility, one or more retail facilities at a single geographic location,and/or a plurality of retail facilities geographically distributed. Insome cases, two or more entities may represent portions of the samelegal entity or affiliates. For example, the offline store 102 anddistributors may be departments within one enterprise. In summary, theoffline store 102 may wirelessly execute financial transactions with themobile device 110.

Each mobile device 110 comprises an electronic device operable tointerface with the transaction card 112 a. For example, the mobiledevice 110 may receive and transmit wireless and/or contactlesscommunication with the system 100. As used in this disclosure, themobile devices 110 are intended to encompass cellular phones, dataphones, pagers, portable computers, SIP phones, smart phones, personaldata assistants (PDAs), digital cameras, MP3 players, camcorders, one ormore processors within these or other devices, or any other suitableprocessing devices capable of communicating information with thetransaction card 112. In some implementations, the mobile devices 110may be based on a cellular radio technology. For example, the mobiledevice 110 may be a PDA operable to wirelessly connect with an externalor unsecured network. In another example, the mobile device 110 maycomprise a smartphone that includes an input device, such as a keypad,touch screen, mouse, or other device that can accept information, and anoutput device that conveys information associated with a transactionwith the offline store 102, including digital data, visual information,or GUI 111.

The GUI 111 comprises a graphical user interface operable to allow theuser of the mobile device 110 to interface with at least a portion ofthe system 100 for any suitable purpose, such as authorizingtransactions and/or displaying transaction history. Generally, the GUI111 provides the particular user with an efficient and user-friendlypresentation of data provided by or communicated within the system 100and/or also an efficient and user-friendly means for the user toself-manage settings and access services offered by the financialinstitution 106. The GUI 111 may comprise a plurality of customizableframes or views having interactive fields, pull-down lists, and/orbuttons operated by the user. The term graphical user interface may beused in the singular or in the plural to describe one or more graphicaluser interfaces and each of the displays of a particular graphical userinterface. The GUI 111 can include any graphical user interface, such asa generic web browser or touch screen, that processes information in thesystem 100 and presents the results to the user.

The transaction card 112 can include any software, hardware, and/orfirmware configured to wirelessly execute transactions with the POSdevice 114. For example, the transaction card 112 may execute acontactless transaction with the POS device 114 independent of themobile device 110 a. In other words, the transaction card 112 maywirelessly execute transactions without aspects of the transaction beingexecuted by the mobile device 110. The transaction card 112 may executetransactions with the POS device 114 using short range signals such asNFC (e.g., ISO 18092/ECMA 340), ISO 14443 type A/B, ISO 15693, Felica,MiFARE, Bluetooth, Ultra-wideband (UWB), Radio Frequency Identifier(RFID), contactless signals, proximity signals, and/or other signalscompatible with retail payment terminals (e.g., POS 114). In someimplementations, the transaction card 112 may include one or morechipsets that execute an operating system and security processes toindependently execute the transaction. In doing so, the mobile device110 does not require additional hardware, software, and/or firmware towirelessly execution a transaction with the POS 114 such as an NFCtransaction. In some implementations, the transaction card 112 mayexecute one or more of the following: wirelessly receive a request fromthe POS device 114 to execute a transaction and/or and provide aresponse; translate between wireless protocols and protocols compatiblewith the transaction card 112; translate between transaction-cardprotocols and protocols compatible with mobile device 110; present andreceive information (e.g., PIN request, PIN) from the user through theGUI 111; decrypt and encrypt information wirelessly transmitted betweenthe transaction card 112 and the POS 114; execute applications locallystored in the transaction card 112; selectively switch the antenna ofthe transaction card 112 on and off based, at least in part, on one ormore events; execute authentication processes based, at least in part,on information received, for example, through the GUI 111; transmit ahost signature to POS 114 in response to at least a transactionchallenge; store, at least in part, details of the transaction executedbetween place between the card 112 and the POS device 114; generateand/or present alerts (e.g., audio-visual alerts) to the user throughthe GUI 111; generate and/or transmit wireless-message alerts to thefinancial institution 106 using the mobile device 110 if cellularcapable; and/or others. In some implementations, the transaction card112 may include a communication module with of a protocol translationmodule, antenna tuning circuit, power circuit and a miniature antennatuned to exchange wireless data with a retail terminal 114.

In some implementations, the transaction card 112 may initiate atransaction in response to at least a user selecting a graphical elementin the GUI 111. The transaction card 112 may initiate a transaction withthe POS 114 in response to at least wireless request transmitted by thePOS 114. In some implementations, the transaction card 112 mayselectively switch the antenna between an on and off state in responseto one or more events. The one or more events may include a userrequest, completion of transaction, insertion of card 112 in a differentmobile device, location change, timer events, detection of incorrect PINentered by the user, change of wireless network that the device isconnected to, message received from the financial institution 106 usingwireless communication methods such as SMS, and/or other events. Forexample, the transaction card 112 may receive one or more commands toswitch the antenna off from a cellular network (not illustrated) throughthe mobile device 110. In some implementations, the transaction card 112may request user identification such as a PIN, a user ID and passwordcombination, biometric signature, and/or others.

In regards to translating between protocols, the transaction card 112may process information in, for example, ISO 7816, a standard securityprotocol, and/or others. In this case, the transaction card 112 maytranslate between an NFC protocol (e.g., ISO 18092) and thetransaction-card protocol. In some implementations, ISO 7816 commandsmay be encapsulated within interface commands used to transmit databetween the host device 114 and the card 112. In addition, thetransaction card 112 may interface the mobile device 110 through aphysical interface such as MicroSD, Mini-SD SD, MMC, miniMMC, microMMC,USB, miniUSB, microUSB, firewire, Apple iDock, and/or others. In regardto security processes, the transaction card 112 may implement one ormore encryption algorithms to secure transaction information such ascard number (e.g., credit card number, debit-card number, bank accountnumber), PIN, and/or other security related information. The securityrelated information may include an expiry date, card verification code,user name, home phone number, user zip code and/or other userinformation associated with verifying an identity of the card holder. Insome implementations, the transaction card 112 may execute private key(symmetric algorithms) such as DES, TDES and/or others or public key(asymmetric algorithms) such as RSA, elliptic curves, and/or others. Inaddition, the transaction card 112 may include memory (e.g., Flash,EEPROM) for storing user data, applications, offline Webpages, and/orother information. In regards to applications, the transaction card 112may execute a locally stored application and present information to andreceived information from the user through the GUI 111. For example, thetransaction card 112 may execute an application used to synchronize anaccount balance with the financial institution 106 using the GUI 111 andthe mobile device 110. Alternatively or in addition to applications, thetransaction card 112 may present offline Web pages to the user using theGUI 111. In response to initiating a transaction, the transaction card112 may automatically present an offline Web page through the GUI 111.In some implementations, the offline Web page can be associated with afinancial institution 106. In some implementations, the transaction card112 can be backward compatible and operate as a mass storage device. Forexample, if the wireless interface of the transaction card 112 is notavailable or deactivated, the transaction card 112 may operate as a massstorage device enabling users to access data stored in the memorycomponent (e.g., Flash). In some implementations, the transaction card112 can execute a set of initialization commands in response to at leastinsertion into the mobile device 110. These initialization commands mayinclude determining device related information for the mobile device 100(e.g., phone number, signature, connected network information, locationinformation and other available properties), determining user relatinginformation (e.g., PIN code, activation code), incrementing counters,setting flags and activating/deactivating functions according topre-existing rules and/or algorithms.

In some implementations, the transaction card 112 may automaticallyexecute one or more fraud control processes. For example, thetransaction card 112 may identify an operational change andautomatically transmit a notification to the financial institutionbased, at least in part, on the identified change. The transaction card112 may execute two fraud control processes: (1) determine a violationof one or more rules; and (2) automatically execute one or more actionsin response to at least the violation. In regards to rules, thetransaction card 112 may locally store rules associated with updates tooperational aspects of the transaction card 112. For example, thetransaction card 112 may store a rule indicating a change in mobile hostdevice 110 is an operational violation. In some implementations, thetransaction card 112 may store rules based, at least in part, on updatesto one or more of the following: phone number of host device 110; MACaddress of host device 110; network wirelessly connected to host device110; location of host device; and/or other aspects. In response to oneor more events matching or otherwise violating rules, the transactioncard 112 may execute one or more processes to substantially prevent orotherwise notify the financial institutions 106 of potentiallyfraudulent activity. For example, the transaction card 112 may execute acommand to block an associated user account and/or the transaction card112. Alternatively or in addition, the transaction card 112 may transmita command to the financial institution 106 to call the mobile hostdevice 110. In some implementations, the transaction card 112 mayexecute a command based, at least in part, on an event type. In someexamples, the transaction card 112 may initiate a call with thefinancial institution 106 in response to at least a change in number ofthe host device 110. In some examples, the transaction card 112 mayre-execute an activation process in response to at least a specifiedevent type. An activation process may include activating the transactioncard and/or financial account as discussed in more detail with respectto FIG. 9. In some implementations, the transaction card 112 may executea command to disconnect the GUI 111 from the transaction card 112. Thetransaction card 112 may present a disconnection notification throughthe GUI 111 prior to executing the command. In some implementations, thetransaction card 112 may transmit a command to the financial institution106 to deactivate an account associated with the card 112.

In some implementations, the POS 114 may transmit a transaction request117 to the transaction card 112 for information to generate anauthorization request 118. In response to at least the transactionrequest, the transaction card 112 may transmit one or more transactionresponses 119 identifying information associated with a payment account.In some implementations, the POS device 114 may transmit a request 118to authorize a transaction to the financial institution 106. Theauthorization information may include an account number, a transactionamount, user credentials, and/or other information. In response to atleast the transaction request 118, the financial institution 106 maytransmit an authorization response 120 to the POS device 114. In someimplementations, the POS device 114 may transmit the response 120 to thetransaction card 112. The transaction response 120 may include, forexample, a receipt presentable to the user through the GUI 111 a. Insome implementations, the financial institution 106 may transmit theauthorization response 120 to the mobile device through a cellular corenetwork (see FIG. 2). In this implementation, the financial institution106 may have stored the association between the mobile device 110 andthe transaction card 112 during the user sign-up process, automaticallyupon user activation of the card 112 when, for example, the card 112 isinitially inserted into the mobile device 110, and/or other event. Inthe illustrated implementation, the POS 114 includes the GUI 109.

The GUI 109 comprises a graphical user interface operable to allow theuser of the POS 114 to interface with at least a portion of the system100 for any suitable purpose, such as a user entering transactioninformation (e.g., PIN, transaction acceptance) and/or and presentingtransaction information (e.g., transaction amount). Generally, the GUI109 provides the particular user with an efficient and user-friendlypresentation of data provided by or communicated within the system 100and/or also an efficient and user-friendly means for the user toinitiate a wirelessly transaction with the transaction card 112. The GUI109 may present a series of screens or displays to the user to, forexample, accept a transaction and enter security information such as aPIN.

In some implementations, the transaction card 112 can be implementeddifferently. The transaction card 112 may be implemented as a KeyFOB andremains live outside the mobile device 110 as a FOB. In this case, thetransaction card 112 may be passive and powered from an inductionmagnetic field generated by the POS 114. The transaction card 112 may beimplemented in the form of an industrial integrated circuit chip formounting on a PCB or IC chip. In some implementations, the transactioncard 112 may be implemented in the form of a self contained desktopstandalone unit powered by external AC adapter or stand alone box. Insome implementations, the transaction card 112 can be implemented as anexternal attachment to a mobile device 110 (e.g., case) and connected tothe mobile device using a peripheral interface such as USB, serial port,the iDock apple proprietary interface, and/or other interface.

In some implementations, the transaction card 112 may operate inaccordance with one or more of the following modes: active cardemulation; active reader; self train; killed; memory; inactive; and/orother modes. The transaction card 112 may operate active-card-emulationmode to convert the mobile device 110 to a contactless payment deviceloaded with a financial vehicle (FV) that may be, for example, a creditcard, a debit card, a gift card and/or other retail payment product. Inthis mode, the transaction card 112 may execute payment transactions atany capable retail payment terminal (e.g., POS 114) that acceptscontactless payment transactions. For example, such terminals may becontactless-enabled terminals currently being deployed by merchantsunder MasterCard's paypass, Visa's paywave programs, Amex ExpressPay,Discover Zip, and/or other payment programs. After the antenna of thetransaction card 112 is activated in this mode, a merchant terminal maydetect the presence of a host device with the transaction card 112 andprompt the user to authorize a transaction such as by entering a PIN,signing on a terminal interface, confirming the amount of thetransaction, and/or other action. In this mode, such transactions may behandled as a normal card-present transaction. In other words, the POS114 may perceive the transaction card 112 as a contactless plasticpayment card and may communicate with the transaction card 112 as acontactless plastic payment card to execute payment transactions. Inthese implementations when the card 112 operates in an active-cardemulation mode, the POS 114 can wirelessly communicate with thetransaction card 112 using the same signals used to communicate with acontactless plastic payment card. In this active-card emulation mode,the transaction card 112 emulates a contactless plastic payment card andmay be backward compatible with the POS 114. In this implementation,neither the terminal nor the financial institution may requireadditional software to execute the transaction. In addition, thetransaction card 112 in this mode may be used for other applicationssuch as physical access control (to open gates either in a corporateenvironment or in a transit environment), logical access control (torequest network access via a PC), application access control (to buyaccess for amenities such as transportation, movies or wherever paymentneeds to be made to gain access to a facility), and/or otherapplications.

In the active-reader mode, the transaction card 112 may convert themobile device 110 to a contactless reader device capable of receivingdata when in range of a transmitting terminal (e.g., POS 114). In someimplementations, this mode can require special NFC hardware with readermode capability as part of the transaction card 112. In the event thatthe mobile device 110 is proximate (e.g., 10 cm or less) a transmittingterminal, the reader mode of the transaction card 112 may activated andprompt the user for authorization to receive data through the GUI 111.This mode may only be suitable for mobile devices 110 with a UI element,such as an OK button and a screen, an LED to indicate that datareception is being requested, and/or other interfaces. Once the userauthorizes the transmission, the transaction card 112 in this mode mayreceive, and locally store, process and may execute a transaction and/orforward received data to another entity. For example, the transactioncard 112 in this mode may receive content through promotional posters,validating the purchase of a ticket, and/or others. For example, thetransaction card 112 in this mode may function as a mobile POS terminalreceiving transaction information from a plastic contactless card/FOBand instructing the POS 114 to prepare a transaction authorizationrequest for the financial institution 106 through a cellular corenetwork. Once the financial institution 106 authorizes the transaction,the mobile device 110 may display the confirmation of the transaction tothe user through the GUI 111.

In regards to the self-train mode, the transaction card 112 may executea version of the reader mode. In some implementations, the self-trainmode can be activated by a special action (e.g., a needle point press toa small switch, entry of an administrative password via the GUI 111). Inresponse to at least activating this mode, the transaction card 112 maybe configured to receive personalization data over, for example, theshort range wireless interface from another peer transaction card suchas the plastic contactless cards compliant with this functionality andissued by the financial institution 106 or a specially preparedadministrative card for this purpose. Personalization data received inthis mode may include encrypted FV information that is stored in securedmemory of the transaction card 112. In some implementations, thetransaction card 112 in this mode may receive the FV information througha contactless interface of a transmitter and/or others. The transactioncard 112 may then synthesize the FV information that corresponds to theuser account and personalize an internal security module that includes,for example, payment applications for executing transactions withfinancial institutions 106 and associated user credentials. Theself-train mode may be used to re-personalize the transaction card 112in the field. In some implementations, all previous data can be deletedif the self-train mode is activated. The self-train mode may be apeer-to-peer personalization mode where the card 112 may receivepersonalization information from another transaction card 112. This modemay represent an additional personalization mode as compared withfactory, store and/or Over-The-Air (OTA) personalization scenarios whichmay be server to client personalization scenarios. In someimplementations, the self-train mode may be a peer-to-peerpersonalization mode where the transaction card 112 receivespersonalization information from another transaction card. Since twotransaction cards 112 are used in this mode, this mode may be differentfrom a server-to-client personalization scenario as with a factory,store, and OTA personalization.

In regards to the inactive mode, the transaction card 112 maytemporarily deactivate the contactless interface. In someimplementations, the inactive mode can be activated through the physicalinterface with the mobile device 110 such as a microSD interface. Inresponse to at least the activation of the inactive mode, thetransaction card 112 may temporarily behave as only a mass-memory card.In some implementations, the card 112 may also enter this state when thereset needle point is pressed. In this mode, the transaction card 112may preserve locally-stored information including financial user data.In this mode, the transaction card 112 may execute the activationprocess and if successful may return to the active mode. Financialinstitutions 106 may use this mode to temporarily prevent usage inresponse to at least identifying at least potentially fraudulentactivity.

In regards to the killed mode, the transaction card 112 may permanentlydeactivate the contactless interface. In some implementations, thekilled mode is activated through the physical interface with the mobiledevice 110 such as a microSD interface. In response to at least theactivation of the killed mode, the transaction card 112 may permanentlybehaves as a mass memory stick. In the event that the reset needle pointis pressed, the transaction card 112 may, in some implementations, notbe made to enter any other modes. In addition, the transaction card 112may delete financial content in memory in response to at least this modebeing activated. In some implementations, financial institutions 106 mayuse this mode to delete data from a transaction card 112 that isphysically lost but still connected to the wireless network via the hostdevice 110.

In regards to the memory mode, the transaction card 112 may operate as amass memory stick such that the memory is accessible throughconventional methods. In some implementations, the transaction card 112may automatically activate this mode in response to at least beingremoved from the host device, inserted into a non-authorized hostdevice, and/or other events. The transaction card 112 may be switched toactive mode from the memory mode by, for example, inserting the card 112into an authorized device or may be switched from this mode into theself-train mode to re-personalize the device for a new host device or anew user account. In some implementations, the memory mode may operatesubstantially same as the inactive mode.

In some implementations, the transaction card 112 may bere-personalized/updated such as using software device management processand/or a hardware reset. For example, the user may want tore-personalize the transaction card 112 to change host devices, to havemultiple host devices, and/or other reasons. In regards to the softwaredevice management, the user may need to cradle the new host device withthe transaction card 112 inserted to launch the software devicemanagement application. In some implementations, the software managementapplication can be an application directly installed on the client 104,integrated as a plug-in to a normal synchronization application such asActiveSync, available via a browser plug-in running on the plug-inprovider's website, and/or other sources. The user may log into theapplication and verify their identity, and in response to verification,the application may allow access to a devices section in the devicemanagement application. The device management application may read thetransaction card 112 and display the MAC addresses, signatures of thedevices that he has inserted his plug-in to, and/or other devicespecific information. The mobile device 110 may be marked as active andthe host device may be shown as disallowed or inactive. The applicationmay enable the user to update the status of the new host device, and inresponse to at least the selection, the device management applicationmay install the signature on the new host device and mark update thestatus as allowable in secure memory of the transaction card 112. Theuser may be able to also update the status of the mobile device 110 todisallowed. Otherwise, both devices may be active and the transactioncard 112 may be switched between the two devices. In regards to thehardware reset process, the use may use the reset needle point press onthe physical transaction card 112 to activate the self-train mode. Inthis mode, the financial data may be deleted and have to be reloaded.When the transaction card 112 is inserted into the new host device, theprovisioning process may begin as discussed above.

The POS 114 can include any software, hardware, and/or firmware thatreceives from the transaction card 112 account information for executinga transaction with one or more financial institutions 106. For example,the POS 114 may be an electronic cash register capable of wirelesslycommunicating transaction information with the transaction card 112 a.The POS 114 may communicate transaction information associated withtraditional contact payment methods such as plastic cards and checks. Ifenabled for wireless/contactless payment transactions, the POS 114 maycommunicate information with the transaction card 112 in one or more thefollowing formats: 14443 Type A/B, Felica, MiFare, ISO 18092, ISO 15693;and/or others. The transaction information may include verificationinformation, check number, routing number, account number, transactionamount, time, driver's license number, merchant ID, merchant parameters,credit-card number, debit-card number, digital signature and/or otherinformation. In some implementations, the transaction information may beencrypted. In illustrated implementation, the POS 114 can wirelesslyreceive encrypted transaction information from the transaction card 112and electronically send the information to one or more of the financialinstitutions 106 for authorization. For example, the POS 114 may receivean indication that a transaction amount has been accepted or declinedfor the identified account and/or request additional information fromthe transaction card 112.

As used in this disclosure, the client 104 are intended to encompass apersonal computer, touch screen terminal, workstation, network computer,a desktop, kiosk, wireless data port, smart phone, PDA, one or moreprocessors within these or other devices, or any other suitableprocessing or electronic device used for viewing transaction informationassociated with the transaction card 112. For example, the client 104may be a PDA operable to wirelessly connect with an external orunsecured network. In another example, the client 104 may comprise alaptop that includes an input device, such as a keypad, touch screen,mouse, or other device that can accept information, and an output devicethat conveys information associated with transactions executed with thefinancial institutions 106, including digital data, visual information,or GUI 115. In some implementations, the client 104 b can wirelesslycommunicate with the transaction card 112 b using, for example, an NFCprotocol. In some implementations, the client 104 a includes a cardreader 116 having a physical interface for communicating with thetransaction card 112 c. In some implementations, the card reader 116 mayat least include an adapter 116 b that adapts the interface supported bythe client 104 (e.g., USB, Firewire, Bluetooth, WiFi) to the physicalinterface supported by the card 112 (e.g., SD/NFC). In this case, theclient 104 a may not include a transceiver for wireless communication.

The GUI 115 comprises a graphical user interface operable to allow theuser of the client 104 to interface with at least a portion of thesystem 100 for any suitable purpose, such as viewing transactioninformation. Generally, the GUI 115 provides the particular user with anefficient and user-friendly presentation of data provided by orcommunicated within the system 100. The GUI 115 may comprise a pluralityof customizable frames or views having interactive fields, pull-downlists, and/or buttons operated by the user. The term graphical userinterface may be used in the singular or in the plural to describe oneor more graphical user interfaces and each of the displays of aparticular graphical user interface. The GUI 115 can include anygraphical user interface, such as a generic web browser or touch screen,that processes information in the system 100 and presents the results tothe user. The financial institutions 106 can accept data from the client104 using, for example, the web browser (e.g., Microsoft InternetExplorer or Mozilla Firefox) and return the appropriate responses (e.g.,HTML or XML) to the browser using the network 108. In someimplementations, the GUI 111 c of the transaction card 112 c may bepresented through the GUI 115 a of the client 104 a. In theseimplementations, the GUI 115 a may retrieve user credentials from theGUI 111 c and populate financial forms presented in the GUI 115 a. Forexample, the GUI 115 a may present a forum to the user for enteringcredit card information to purchase a good through the Internet, and theGUI 115 a may populate the form using the GUI 111 c in response to atleast a request from the user.

Financial institutions 106 a-c can include any enterprise that mayauthorize transactions received through the network 108. For example,the financial institution 106 a may be a credit card provider thatdetermines whether to authorize a transaction based, at least in part,on information received through the network 106. The financialinstitution 106 may be a credit card provider, a bank, an association(e.g., VISA), a retail merchant (e.g., Target), a prepaid/gift cardprovider, an internet bank, and/or others. In general, the financialinstitution 106 may execute one or more of the following: receive arequest to authorize a transaction; identify an account number and othertransaction information (e.g., PIN); identify funds and/or a creditlimit associated with the identified account; determine whether thetransaction request exceeds the funds and/or credit limit and/orviolates any other rules associated with the account; transmit anindication whether the transaction has been accepted or declined; and/orother processes. In regards to banking, the financial institution 106may identify an account number (e.g., bank account, debit-card number)and associated verification information (e.g., PIN, zip code) anddetermine funds available to the account holder. Based, at least inpart, on the identified funds, the financial institution 106 may eitheraccept or reject the requested transaction or request additionalinformation. As for encryption, the financial institution 106 may use apublic key algorithm such as RSA or elliptic curves and/or private keyalgorithms such as TDES to encrypt and decrypt data.

Network 108 facilitates wireless or wired communication between thefinancial institutions and any other local or remote computer, such asclients 104 and the POS device 114. Network 108 may be all or a portionof an enterprise or secured network. While illustrated as singlenetwork, network 108 may be a continuous network logically divided intovarious sub-nets or virtual networks without departing from the scope ofthis disclosure, so long as at least a portion of network 108 mayfacilitate communications of transaction information between thefinancial institutions 106, the clients 104, and the offline store 102.In some implementations, network 108 encompasses any internal orexternal network, networks, sub-network, or combination thereof operableto facilitate communications between various computing components insystem 100. Network 108 may communicate, for example, Internet Protocol(IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM)cells, voice, video, data, and other suitable information betweennetwork addresses. Network 108 may include one or more local areanetworks (LANs), radio access networks (RANs), metropolitan areanetworks (MANs), wide area networks (WANs), all or a portion of theglobal computer network known as the Internet, and/or any othercommunication system or systems at one or more locations.

FIG. 2 is a block diagram illustrating an example transaction system 200for wirelessly communicating transactions information using cellularradio technology. For example, the system 200 may wirelessly communicatea transaction receipt to a transaction card 112 using a mobile hostdevice 110 and cellular radio technology. In some implementations,cellular radio technology may include Global System for MobileCommunication (GSM), Code Division Multiple Access (CDMA), UniversalMobile Telecommunications System (UMTS), and/or any other cellulartechnology. The financial institutions 106 may assign one or more mobilehost devices 110 to a transaction card 112 in response to one or moreevents. In some examples, the user may register the one or more mobiledevices 110 with the financial institution 106 in connection with, forexample, requesting the associated transaction card 112. In someexamples, the transaction card 112 may register the mobile host device110 with the financial institution 106 in response to at least aninitial insertion into the device 110. Regardless of the associationprocess, the system 100 may use the cellular capabilities of the hostdevices 110 to communicate information between the financialinstitutions 106 and the transaction card 112. In using the cellularradio technology of the host device 110, the system 100 may communicatewith the transaction card 112 when the card 112 is not proximate aretail device, such as the POS device 114 of FIG. 1.

In the illustrated implementation, the cellular core network 202typically includes various switching elements, gateways and servicecontrol functions for providing cellular services. The cellular corenetwork 202 often provides these services via a number of cellularaccess networks (e.g., RAN) and also interfaces the cellular system withother communication systems such as the network 108 via a MSC 206. Inaccordance with the cellular standards, the cellular core network 202may include a circuit switched (or voice switching) portion forprocessing voice calls and a packet switched (or data switching) portionfor supporting data transfers such as, for example, e-mail messages andweb browsing. The circuit switched portion includes MSC 206 thatswitches or connects telephone calls between radio access network (RAN)204 and the network 108 or another network, between cellular corenetworks or others. In case the core network 202 is a GSM core network,the core network 202 can include a packet-switched portion, also knownas General Packet Radio Service (GPRS), including a Serving GPRS SupportNode (SGSN) (not illustrated), similar to MSC 206, for serving andtracking communication devices 102, and a Gateway GPRS Support Node(GGSN) (not illustrated) for establishing connections betweenpacket-switched networks and communication devices 110. The SGSN mayalso contain subscriber data useful for establishing and handing overcall connections. The cellular core network 202 may also include a homelocation register (HLR) for maintaining “permanent” subscriber data anda visitor location register (VLR) (and/or an SGSN) for “temporarily”maintaining subscriber data retrieved from the HLR and up-to-dateinformation on the location of those communications devices 110 using awireless communications method. In addition, the cellular core network202 may include Authentication, Authorization, and Accounting (AAA) thatperforms the role of authenticating, authorizing, and accounting fordevices 110 operable to access GSM core network 202. While thedescription of the core network 202 is described with respect to GSMnetworks, the core network 202 may include other cellular radiotechnologies such as UMTS, CDMA, and others without departing from thescope of this disclosure.

The RAN 204 provides a radio interface between mobile devices and thecellular core network 202 which may provide real-time voice, data, andmultimedia services (e.g., a call) to mobile devices through a macrocell208. In general, the RAN 204 communicates air frames via radio frequency(RF) links. In particular, the RAN 204 converts between air frames tophysical link based messages for transmission through the cellular corenetwork 202. The RAN 204 may implement, for example, one of thefollowing wireless interface standards during transmission: AdvancedMobile Phone Service (AMPS), GSM standards, Code Division MultipleAccess (CDMA), Time Division Multiple Access (TDMA), IS-54 (TDMA),General Packet Radio Service (GPRS), Enhanced Data Rates for GlobalEvolution (EDGE), or proprietary radio interfaces. Users may subscribeto the RAN 204, for example, to receive cellular telephone service,Global Positioning System (GPS) service, XM radio service, etc.

The RAN 204 may include Base Stations (BS) 210 connected to Base StationControllers (BSC) 212. BS 210 receives and transmits air frames within ageographic region of RAN 204 (i.e. transmitted by a cellular device 102e) and communicates with other mobile devices 110 connected to the GSMcore network 202. Each BSC 212 is associated with one or more BS 210 andcontrols the associated BS 210. For example, BSC 212 may providefunctions such as handover, cell configuration data, control of RF powerlevels or any other suitable functions for managing radio resource androuting signals to and from BS 210. MSC 206 handles access to BSC 212and the network 108. MSC 206 may be connected to BSC 212 through astandard interface such as the A-interface. While the elements of RAN204 are describe with respect to GSM networks, the RAN 204 may includeother cellular technologies such as UMTS, CDMA, and/or others. In thecase of UMTS, the RAN 204 may include Node B and Radio NetworkControllers (RNC).

The contactless smart card 214 is a pocket-sized card with embeddedintegrated circuits that process information. For example, the smartcard 214 may wirelessly receive transaction information, process theinformation using embedded applications and wirelessly transmit aresponse. The contactless smart card 214 may wirelessly communicate withcard readers through RFID induction technology at data rates of 106 to848 kbit/s. The card 214 may wirelessly communicate with proximatereaders between 10 cm (e.g., ISO/IEC 14443) to 50 cm (e.g., ISO 15693).The contactless smart card 214 operates independent of an internal powersupply and captures energy from incident radio-frequency interrogationsignals to power the embedded electronics. The smart card 214 may be amemory card or microprocessor card. In general, memory cards includeonly non-volatile memory storage components and may include somespecific security logic. Microprocessor cards include volatile memoryand microprocessor components. In some implementations, the smart card214 can have dimensions of normally credit card size (e.g.,85.60×53.98×0.76 mm, 5×15×0.76 mm). In some implementations, the smartcard 214 may be a fob or other security token. The smart card 214 mayinclude a security system with tamper-resistant properties (e.g., asecure cryptoprocessor, secure file system, human-readable features)and/or may be configured to provide security services (e.g.,confidentiality of stored information).

In some aspects of operation, the financial institution 106 may use themobile host device 110 to communicate information to the transactioncard 112. For example, the financial institution 106 may wirelesslycommunicate with the mobile host device 110 using the cellular corenetwork 202. In some implementations, the financial institution 106 maytransmit information to the mobile host device 110 in response to atleast an event. The information may include, for example, transactioninformation (e.g., transaction receipt, transaction history), scripts,applications, Web pages, and/or other information associated with thefinancial institutions 106. The event may include completing atransaction, determining a transaction card 112 is outside the operatingrange of a POS terminal, receiving a request from a user of the mobilehost device, and/or others. For example, the financial institution 106may identify a mobile host device 110 associated with a card 112 thatexecuted a transaction and transmit transaction information to themobile host device 110 using the cellular core network 202. In using thecellular core network 202, the financial institutions 106 may transmitinformation to the transaction card 112 without requiring a POS terminalbeing proximate to the card 112. In addition or alternatively, thefinancial institution 106 may request information from the mobile hostdevice 110, the transaction card 112 and/or the user using the cellularcore network 202. For example, the financial institution 106 maytransmit a request for transaction history to the card 112 through thecellular core network 202 and the mobile host device 110.

In some aspects of operation, a merchant or other entity may operate themobile host device 110 c as a mobile POS terminal configured towirelessly execute transactions with the smart card 214. For example, avendor may be mobile (e.g., a taxi driver) and may include a mobile hostdevice 110 c with a transaction card 112 c. In this example, thetransaction card 112 c may wirelessly receive account information fromthe smart card 214 and the POS 114 may transmit an authorization requestto the financial institution 106 using the mobile host device 110 andthe cellular core network 202. In response to at least the request, thefinancial institution 106 may generate an authorization response to thetransaction card 112 c using the mobile host device 110 and the cellularnetwork 202.

In some implementations, the system 100 may execute one or more of themodes discussed with respect to FIG. 1. For example, the transactioncard 112 may be re-personalized/updated using the cellular radiotechnology of the mobile host device 110. The user may want tore-personalize the transaction card 112 to change host devices, to havemultiple host devices, and/or other reasons. In regards to the softwaredevice management, the user may transmit to the financial institution106 a request to re-personalize the transaction card 112 using thecellular radio technology of the host device 110.

FIG. 3 illustrates is a block diagram illustrating an exampletransaction card 112 of FIG. 1 in accordance with some implementationsof the present disclosure. In general, the transaction card 112 includespersonalized modules that execute financial transactions independent ofthe mobile device 110. The illustrated transaction card 112 is forexample purposes only, and the transaction card 112 may include some,all or different modules without departing from the scope of thisdisclosure.

In some implementations, the transaction card 112 can include aninterface layer 302, an API/UI 304, a Web server 306, a real-timeframework 308, payment applications 310, value added applications 312,user credentials 314, real-time OS 316, contactless chipset 318, antennacontrol functions 320, antenna 322, bank used memory 324, and freememory 326. In some implementations, a host controller includes theinterface layer 302, he API/UTI 304, the Web server 306, the real-timeframework 308, the contactless chipset 318, and the antenna controlfunctions 320. In some implementations, a security module includes thepayment applications 310 and the user credentials 314. The bank usedmemory 324 and free memory 326 may be contained in Flash. In someimplementations, the contactless chipset 318 may be integrated withinthe security module or operated as a standalone. The antenna 322 may beelectronic circuitry.

The interface layer 302 includes interfaces to both the host device,i.e., physical connection, and the external world, i.e.,wireless/contactless connection. In payment implementations, thewireless connection can be based on any suitable wireless standard suchas contactless (e.g., ISP 14443 A/B), proximity (e.g., ISO 15693), NFC(e.g., ISO 18092), and/or others. In some implementations, the wirelessconnection can use another short range wireless protocol such asBluetooth, another proprietary interfaces used by retail paymentterminals (Felica in Japan, MiFare in Asia, etc.), and/or others. Inregards to the physical interface, the interface layer 302 mayphysically interface the mobile device 110 using an SD protocol such asMicroSD, Mini-SD or SD (full-size). In some implementations, thephysical interface may include a converter/adapter to convert betweentwo different protocols based, at least in part, on the mobile device110. In some implementations, the mobile device 110 may communicateusing protocols such as USB, MMC, iPhone proprietary interface, orothers.

The API/UI layer 304 can include any software, hardware, and/or firmwarethat operates as an API between the mobile device 110 and thetransaction card 112 and as the GUI 111. Prior to executingtransactions, the transaction card 112 may automatically install driversin the mobile device 110 in response to at least insertion. For example,the transaction card 112 may automatically install a MicroSD devicedriver in the device 110 to enable the transaction card 112 to interfacethe mobile device 110. In some implementations, the transaction card 112may install an enhanced device driver such as a Mass Memory with Radio(MMR) API. In this implementation, the interface can drive a class ofplug-ins that contain mass memory as well as a radio interface. The MMRAPI may execute one or more of the following: connect/disconnect to/fromthe MMR controller (Microcontroller in the plug-in); transfer data usingMM protocol (e.g., SD, MMC, XD, USB, Firewire); send encrypted data tothe MMR controller; receive Acknowledgement of Success or Error;received status word indicating description of error; turn radio on/off;send instruction to the transaction card 112 to turn the antenna on withspecifying the mode of operation (e.g., sending mode, listening mode);transmit data such as send instruction to controller to transmit datavia the radio; listen for data such as send instruction to controller tolisten for data; read data such as send instruction to controller tosend the data received by the listening radio; and/or others. In someimplementations, MMR can be compliant with TCP/IP. In someimplementations, API encapsulated ISO 7816 commands may be processed bythe security module in addition to other commands.

In some implementations, the API can operate in accordance with the twoprocesses: (1) the transaction card 112 as the master and the mobiledevice 110 as the slave; and (2) the card UI as the master. In the firstprocess, the transaction card 112 may pass one or more commands to themobile device 110 in response to, for example, insertion of thetransaction card 112 into a slot in the mobile device 110, a transactionbetween the transaction card 112 and the POS 114, and/or other events.In some implementations, the transaction card 112 can request the mobiledevice 110 to execute one or more of following functions: Get UserInput; Get Signature; Display Data; Send Data; Receive Data; and/orothers. The Get User Input command may present a request through the GUI111 for data from the user. In some implementations, the Get User Inputmay present a request for multiple data inputs. The data inputs may beany suitable format such as numeric, alphanumeric, and/or other stringsof characters. The Get Signature command may request the mobile device110 to return identification data such as, for example, a phone number,a device ID like an IMEI code or a MAC address, a network code, asubscription ID like the SIM card number, a connection status, locationinformation, Wi-Fi beacons, GPS data, and/or other device specificinformation. The Display Data command may present a dialog to the userthrough the GUI 111. In some implementations, the dialog can disappearafter a period of time, a user selection, and/or other event. The SendData command may request the mobile device 110 to transmit packet datausing its own connection to the external world (e.g., SMS, cellular,Wi-Fi). The Receive Data command may request the mobile device 110 toopen a connection channel with certain parameters and identify datareceived through the connection. In some implementations, the commandcan request the mobile device 110 to forward any data (e.g., SMS)satisfying certain criteria to be forwarded to the transaction card 112.

In regards to the UI as master, the UI may execute one or more of thefollowing commands: security module Command/Response;Activate/Deactivate; Flash Memory Read/Write; Send Data with or withoutencryption; Receive Data with or without decryption; URL Get Data/URLPost Data; and/or others. The security module commands may relate tosecurity functions provided by the card and are directed towards thesecurity module within the transaction card 112 (e.g., standard ISO 7816command, proprietary commands). In some implementations, the commandsmay include encryption, authentication, provisioning of data, creationof security domains, update of security domain, update of usercredentials after verification of key, and/or others. In someimplementations, the commands may include non security related smartcard commands such as, for example, read transaction history commands.The read transaction history command may perform a read of the securememory 324 of the transaction card 112. In some implementations, certainflags or areas of the secure memory 324 may be written to after securityverification. The Activate/Deactivate command may activate or deactivatecertain functions of the transaction card 112. The Flash MemoryRead/Write command may execute a read/write operation on a specifiedarea of the non-secure memory 326. The Send Data with or withoutencryption command may instruct the transaction card 112 to transmitdata using its wireless connection with, for example, the POS 114. Inaddition, the data may be encrypted by the transaction card 112 prior totransmission using, for example, keys and encryption capability storedwithin the security module. The Receive Data with or without decryptioncommand may instruct the transaction card 112 to switch to listeningmode to receive data from its wireless connection with theterminal/reader (e.g., POS 114). In some implementations, datadecryption can be requested by the security module using, for example,keys and decryption algorithms available on the security module, i.e.,on-board decryption. The URL Get Data/URL Post Data command may instructthe web server 306 to return pages as per offline get or postinstructions using, for example, offline URLs.

The Web server 306, as part of the OS of the transaction card 112, mayassign or otherwise associate URL style addressing to certain filesstored in the memory 326 (e.g., flash) of the transaction card 112. Insome implementations, the Web server 306 locates a file using the URLand returns the file to a browser using standard HTTP, HTTPS styletransfer. In some implementations, the definition of the files can beformatted using standard HTML, XHTML, WML and/or XML style languages.The file may include links that point to additional offline storagelocations in the memory 326 and/or Internet sites that the mobile device110 may access. In some implementations, the Web server 306 may supportsecurity protocols such as SSL. The Web server 306 may transfer anapplication in memory 326 to the mobile device 111 for installation andexecution. The Web server 306 may request the capabilities of thebrowser on the device 110 using, for example, the browser user agentprofile, in order to customize the offline Web page according to thesupported capabilities of the device and the browser, such as, forexample, supported markup language, screen size, resolution, colors andsuch.

As part of the Real time OS, the real-time framework 308 may execute oneor more functions based, at least in part, on one or more periods oftime. For example, the real-time framework 308 may enable an internalclock available on the CPU to provide timestamps in response to at leastrequested events. The real-time framework 308 may allow certain tasks tobe pre-scheduled such that the tasks are executed in response to atleast certain time and/or event based triggers. In some implementations,the real-time framework 308 may allow the CPU to insert delays incertain transactions. In some implementation, a part of WAP standardscalled WTAI (Wireless Telephoney Application Interface) can beimplemented to allow offline browser pages on the card 112 to make useof functions offered by the mobile device 110 (e.g., send/receivewireless data, send/receive SMS, make a voice call, play a ringtoneetc.).

The payment applications 310 can include any software, hardware, and/orfirmware that exchanges transaction information with the retail terminalusing, in some instances, a pre-defined sequence and/or data format. Forexample, the payment applications 310 may generate a response to atransaction request by selecting, extracting or otherwise including usercredentials in the response, in a format compatible with the retailterminal's payment processing application. In some implementations, thepayment applications 310 may execute one or more of the following:transmit properties of the transaction card 112 in response to at leastan identification request received from the POS 114; receive a requestto execute a transaction from, for example, the POS 114; identify usercredentials in the bank-used memory 324 in response to at least therequest; generate a transaction response based, at least in part, on theuser credentials; transmit the transaction response to the POS 114using, for example, a contactless chipset; receive clear data, forexample a random number, from the POS 114 and provide a responsecontaining encrypted data by encrypting the clear data using thecryptographic capabilities of the secure element; transmit the encrypteddata using the contactless chipset 318; increment a transaction counterwith every transaction request received; transmit a value of thetransaction counter in response to a request from the POS 114; storedetails of the transaction request received from the POS 114 into thetransaction history area of the bank used memory 324; transmittransaction history to the CPU of the intelligent card 112 in responseto such a request; receive ISO 7816 requests from the CPU of theintelligent card 112; execute corresponding transactions using thesecure element OS; provide responses back to the CPU; and/or otherprocesses. In generating the transaction response, the paymentapplication 310 may generate the response in a format specified by thepayment network (VISA, MasterCard, Amex, Discover) associated with afinancial institution 106 or a proprietary format owned and defined bythe financial institution 106 and processible by the POS 114. Thetransaction request may include one or more of the following: usercredentials (e.g., account number); expiry data, card verificationnumbers; a transaction count; and/or other card or user information. Insome implementations, the payment application 310 may comprises abrowser application to enable transactions. The browser application 310may be a browser that may be installed if the device 110 is eithermissing a browser or has a browser that is incompatible with the Webserver 306 on the card 112. After installation of such browser 310,future communications between the mobile device 110 and the web-server306 make use the newly installed browser.

The real-time OS 316 may execute or otherwise include one or more of thefollowing: real-time framework 308; a host process that implements thephysical interface between the transaction-card CPU and the mobiledevice 110; an interface that implements the physical interface betweenthe transaction-card CPU and the security module; a memory-managementprocess that implements the ISO 7816 physical interface between thetransaction-card CPU and the memory 324 and/or 326; an application-layerprocess that implements the API and UT capabilities; the Web server 306;antenna-control functions 320; power management; and/or others. In someimplementations, the real-time OS 316 may manage the physical interfacebetween the transaction-card CPU and the secure memory 324 that includesmemory segmentation to allow certain memory areas to be restrictedaccess and/or data buffers/pipes. In some implementations, the securitymodule can include a security module OS provided by the security moduleVendor and may be compliant with Visa and MasterCard specifications. Thesecurity module OS may structure the data in the security module to becompliant with Paypass and/or payWave specifications or any otheravailable contactless retail payment industry specifications. Inaddition, the security module may store host device signatures and allowmodes of the antenna 322 in the secure element 324. In someimplementations, the real-time OS 316 may include a microcontroller OSconfigured to personalizing the secure element 324 such as by, forexample, converting raw FV data (account number, expiry date, CardVerification Number (CVN), other application specific details) intosecure encrypted information. In addition, the microcontroller OS maypresent the card 112 as a MicroSD mass storage to the host device. Themicrocontroller OS may partition the memory into a user section and aprotected device application section. In this example, the deviceapplication section may be used to store provider specific applicationsthat either operate from this segment of the memory or are installed onthe host device from this segment of the memory.

The security module chip may provide tamper-resistant hardware securityfunctions for encryption, authentication, management of user credentialsusing multiple security domains, on-board processing capabilities forpersonalization, access and storage, and/or others. In someimplementations, the security module chip can include the contactlesschipset 318.

The contactless chipset 318 may provides the hardware protocolimplementation and/or drivers for RF communication. For example, thecontactless chipset 318 may include on-board RF circuitry to interfacewith an external world connection using a wireless/contactlessconnection. The wireless connection may be, for example, client to node(terminal/reader/base station), node to client (passive tag), or peer topeer (another transaction card 112).

The antenna control function 320 may controls the availability of the RFantenna. For example, the antenna control function 320 mayactivate/deactivate the antenna 322 in response to, for example,successful authentication, completion of a routine established by the OS316, and/or other event. The antenna 322 may be a short range wirelessantenna connected to an NFC inlay via a software switch such as a NANDGate or other element.

FIG. 4 is a block diagram illustrating an example intelligent card 400in accordance with some implementations of the present disclosure. Forexample, the transaction card of FIG. 1 may be implemented in accordancewith the illustrated intelligent card 400. In general, the intelligentcard 400 may independently access services and/or transactions. Theintelligent card 400 is for illustration purposes only and may includesome, all, or different elements without departing from the scope of thedisclosure.

As illustrated, the intelligent card 400 includes an antenna 402, aswitch plus tuning circuit 404, a security module and contactlesschipset 406, a CPU 408 and memory 410. The antenna 402 wirelesslytransmits and receives signals such as NFC signals. In someimplementations, the switch plus tuning circuit 404 may dynamicallyadjust the impedance of the antenna 402 to tune the transmit and/orreceive frequency. In addition, the switch plus tuning circuit 404 mayselectively switch the antenna 402 on and off in response to at least acommand from the CPU 408. In some implementations, the antenna 402 canbe a short range wireless antenna connected to an NFC inlay via asoftware switch such as an NAND Gate or other element to allow for codefrom the CPU 408 to turn the antenna 402 on and off. In someimplementations, the card 400 may include an NFC inlay (not illustrated)that can be a passive implementation of NFC short range wirelesstechnology deriving power from the reader terminal in order to transmitdata back or a stronger implementation using an eNFC chipset to poweractive reader mode and self-train mode. In addition, the card 400 mayinclude an external needle point reset (not illustrated) that promptsthe CPU 408 to depersonalize the memory or secure element.

The CPU 408 may transmit the switching command in response to an eventsuch as a user request, completion of a transaction, and/or others. Whenswitched on, the security chip and contactless chipset 406 is connectedto the antenna 402 and executes one or more of the following: formatsignals for wireless communication in accordance with one or moreformats; decrypt received messages and encrypt transmitted messages;authenticate user credentials locally stored in the memory 410; and/orother processes. The memory 410 may include a secure and non-securedsection. In this implementation, the secure memory 410 may store one ormore user credentials that are not accessible by the user. In addition,the memory 410 may store offline Web pages, applications, transactionhistory, and/or other data. In some implementations, the memory 410 mayinclude Flash memory from 64 MB to 32 GB. In addition, the memory 410may be partitioned into user memory and device application memory. Thechipset 406 may include a security module that is, for example Visaand/or MasterCard certified for storing financial vehicle data and/or inaccordance with global standards. In addition to a user's financialvehicle, the secure element may store signatures of allowed host devicesand/or antenna modes.

In some implementations, the CPU 408 may switch the antenna 402 betweenactive and inactivate mode based, at least in part, on a personalizationparameter defined by, for example, a user, distributor (e.g., financialinstitution, service provider), and/or others. For example, the CPU 408may activate the antenna 402 when the intelligent card 400 is physicallyconnected to a host device and when a handshake with the host device issuccessfully executed. In some implementations, the CPU 408 mayautomatically deactivate the antenna 402 when the intelligent card 400is removed from the host device. In some implementations, the antenna402 is always active such that the intelligent card 400 may be used as astand-alone access device (e.g., device on a keychain). In regards tothe handshaking process, the CPU 408 may execute one or moreauthentication processes prior to activating the intelligent card 400and/or antenna 402 as illustrated in FIG. 7. For example, the CPU 408may execute a physical authentication, a device authentication, and/or auser authentication. For example, the CPU 408 may activate the antenna402 in response to at least detecting a connection to the physicalinterface with the host device (e.g., SD interface) and successfulinstallation of the device driver for mass memory access (e.g., SDdevice driver) on the host device. In some implementations, deviceauthentication may include physical authentication in addition to asignature comparison of a device signature stored in memory (e.g.,security module (SE)) that was created during first-use (provisioning)to a run-time signature calculated using, for example, a uniqueparameter of the host device. In the event no host device signatureexists in the memory, the CPU 408 may bind with the first compatiblehost device the card 400 is inserted into. A compatible host device maybe a device that can successfully accomplish physical authenticationsuccessfully. If a host-device signature is present in the memory, theCPU 408 compares the stored signature with the real-time signature ofthe current host device. If the signatures match, the CPU 408 mayproceed to complete the bootstrap operation. If the signatures do notmatch, host device is rejected, bootstrap is aborted and the card 400 isreturned to the mode it was before being inserted into the device.

User authentication may include verification of physical connection witha user using a PIN entered by the user, a x.509 type certificate that isunique to the user and stored on the host device, and/or otherprocesses. Device and user authentication may verify a physicalconnection with device through comparison of a device signature and userauthentication through verification of user PIN or certificate. In someimplementations, the user can select a PIN or certificate atprovisioning time. If this case, the CPU 408 may instantiate a softwareplug-in on the host device. For example, a software plug-in may requestthe user for his PIN in real time, read a user certificate installed onthe device (e.g., x.509), and/or others. The operation of the softwareplug-in may be customized by the provider. Regardless, the returned userdata may be compared with user data stored in the memory. In case of asuccessful match, the antenna 402 may be activated. In case of anunsuccessful match of a certificate, then card 400 is deactivated. Incase of unsuccessful PIN match, the user may be requested to repeat PINattempts until a successful match or the number of attempts exceeds athreshold. The disk provider may customize the attempt threshold.

In regards to network authentication, the host device may be a cellphonesuch that the card 400 may request network authentication prior toactivation. For example, the card 400 may be distributed by a WirelessNetwork Operator (WNO) that requires a network authentication. In thisexample, a flag in memory may be set to ON indicating that networkauthentication is required. If the flag is set to ON, a unique identityabout the allowed network is locally stored in memory such a MobileNetwork Code for GSM networks, a NID for CDMA networks, a SSID forbroadband networks, and/or identifiers. If this flag is ON, the CPU 408in response to at least insertion may request a special software plug-into be downloaded to the host device and instantiated. This softwareplug-in may query the host device to respond with network details. Insome cases, the type of unique network identity employed and the methodto deduce it from the host device may be variable and dependent on thenetwork provider and capability of the host device. If thelocally-stored ID matches the request ID, the CPU 408 activated theantenna 402 to enable access or otherwise services are denied.

FIGS. 5A and 5B illustrate an example transaction card 112 in accordancewith some implementations of the present disclosure. In the illustratedimplementation, the transaction card 112 includes a shape and dimensionsexactly the same or substantially similar to a standard MicroSD card.The transaction card 112 includes an antenna 502 for wirelesslycommunicating with, for example, retail terminals (e.g., POS 114) usingRF signals and an SD interface 506 for physically interfacing a device(e.g., mobile device 110). The antenna 502 may be a flat coil (e.g.,copper coil) integrated on one or more layers the MicroSD transactioncard 112, a printed circuit (e.g., copper circuit) etched on one or morelayers of the MicroSD transaction card 112, and/or other configurationfor wirelessly transmitting and receiving RF signals. In someimplementations, the antenna 502 may be substantially planar andadjacent at least a portion of the housing 508 of the transaction card112 (e.g., top, bottom). The antenna 502 may include a width in therange of approximately 9 mm and a length in the range of approximately14 mm. As illustrated in FIG. 5B, the antenna 502 is connected to atransaction circuit 510 (e.g., a contactless chipset) using, forexample, a tuning circuit that tunes the antenna 502 to one or morefrequencies. The one or more frequencies may be based, at least in part,on the terminal and/or type of terminal (e.g., POS 114). For example,the tuning circuit may tune the antenna 502 to 13.56 MHz for ISO 14443related transactions. In some implementations, the antenna 502 mayinclude insulation, using material, for example, ferrite, tosubstantially prevent signals from interfering with the circuit 510,mobile device 110, battery elements, and/or other elements that may beproximate to the transaction card 112. The transaction card 112 mayinclude an amplifier circuit 504 to amplify (e.g., a factor of 10)signals generated by the antenna 502. In some implementations, theamplifier 504 may be of two types. For example, the amplifier 504 may bea passive amplifier that uses passive circuitry to amplify the RFsignals received by the antenna (see FIGS. 13A and 13B) and/or a poweredactive amplifier that uses the energy from the battery of the hostdevice to operate the transaction circuit (see FIG. 14A and FIG. 14B).In some implementations, the transaction card 112 may contain twoadditional RF interface pins 509A and 509B to allow the transaction cardto use an external antenna, for example, an antenna contained in aseparate housing for transactions and/or personalization.

FIGS. 6A and 6B illustrate another example of the transaction card 112in accordance with some implementations of the present disclosure. Inthe illustrated implementation, the transaction card 112 includes athree-dimensional antenna 602. For example, the antenna 602 may includea shape that is substantially helical such as a three-dimensionalantenna coil. In addition, the transaction card 112 may include ahousing 608 enclosing the antenna 602 and a transaction circuit 610. Asillustrated in FIG. 6B, the antenna 602 may include a core 608 thatsubstantially defines a length and a width of a three-dimensional shapeof the antenna 602. In some implementations, the core 608 may comprise amiddle segment of the transaction card 112 such that the width of theantenna coil 602 is substantially similar to the transaction card 112.The core 608 may reflect at least some wireless signals to substantiallyisolate the magnetic field from the transaction circuit 610, the mobiledevice 110, battery elements, and/or other elements proximate theantenna 602 in such a way that the magnetic field is concentrated in adirection substantially pointing away from the host device. Theillustrated antenna 602 can be connected to the transaction circuit 610(e.g., contactless chipset). In some implementations, the antenna 602may be connected to a tuning circuit that substantially tunes theantenna 602 to one or more frequencies compatible with, for example, aretail terminal 114. For example, the tuning circuit may tune theantenna 602 to 13.56 MHz for ISO 14443 related transactions. Thetransaction card 112 may include an amplifier circuit 604 to amplify(e.g., a factor of 10) wireless signals generated by the antenna 602. Insome implementations, the amplifier 604 may be of two types. Forexample, the amplifier 604 may be a passive amplifier that uses passivecircuitry to amplify the RF signals received by the antenna (see FIGS.13A and 13B) and/or a powered active amplifier that uses the energy fromthe battery of the host device to operate the transaction circuit (seeFIG. 14A and FIG. 14B).

FIGS. 7A and 7B illustrate an example transaction card 112 including anexternal antenna 702 in accordance with some implementations of thepresent disclosure. In the illustrated implementation, the transactioncard 112 can include an antenna 702 enclosed in a resilient member 704and external to a housing 706 of the transaction card 112. The antenna702 and the resilient member 704 may extend outside the SD slot duringinsertion of the housing 706. In some cases, the housing 706 may besubstantially inserted into the slot of the device (e.g., mobile device110). In the illustrated implementation, the housing 706 can include ashape and dimensions exactly the same or substantially similar to astandard MicroSD card. The antenna 702 wirelessly communicates with, forexample, retail terminals (e.g., POS 114) using RF signals. In addition,the transaction card 112 may include an SD interface 710 for physicallyinterfacing a device (e.g., mobile device 110). The antenna 702 may be asubstantially planar coil (e.g., copper coil) integrated into one ormore layers, a printed circuit (e.g., copper circuit) etched into one ormore layers, and/or other configuration for wirelessly transmitting andreceiving RF signals. The enclosed antenna 702 and the housing 706 mayform a T shape. In some implementations, the antenna 702 may besubstantially planar and adjacent at least a portion of the housing 708of the transaction card 112 (e.g., top, bottom). The antenna 702 mayinclude a width in the range of approximately 9 mm and a length in therange of approximately 14 mm. The resilient member 704 may be rubber,foam, and/or other flexible material. In some implementations, a flat,cylindrical or other shaped block of ceramic antenna may be used insteadof the resilient member 704 and antenna 702. As illustrated in FIG. 7B,the antenna 702 is connected to a transaction circuit 710 (e.g., acontactless chipset) using, for example, a tuning circuit that tunes theantenna 702 to one or more frequencies. The one or more frequencies maybe based, at least in part, on the terminal and/or type of terminal(e.g., POS 114). For example, the tuning circuit may tune the antenna702 to 13.56 MHz for ISO 14443 related transactions. In someimplementations, the antenna 702 may include insulation using material,for example, ferrite, to substantially isolate and direct magnetic fieldsignals away from interfering with the circuit 710, mobile device 110,battery elements, and/or other elements that may be proximate to thetransaction card 112 in such a way that the magnetic field isconcentrated in a direction substantially pointing away from the hostdevice slot in which the transaction card is inserted. The transactioncard 112 may include an amplifier circuit 712 to amplify (e.g., a factorof 10) signals generated by the antenna 702. In some implementations,the amplifier 712 may be of two types. For example, the amplifier 712may be a passive amplifier that uses passive circuitry to amplify the RFsignals received by the antenna (see FIGS. 13A and 13B) and/or a poweredactive amplifier that uses the energy from the battery of the hostdevice to operate the transaction circuit (see FIG. 14A and FIG. 14B).

FIGS. 8A-C illustrate an example transaction card 112 including anexternal three-dimensional antenna 802 in accordance with someimplementations of the present disclosure. In the illustratedimplementation, the transaction card 112 can include an antenna 802enclosed in a resilient member 804 and external to a housing 806 of thetransaction card 112. The antenna 802 and the resilient member 804 mayextend outside the SD slot receiving the housing 806. In some cases, thehousing 806 may be substantially inserted into the slot of the device(e.g., mobile device 110). In the illustrated implementation, thehousing 806 can include a shape and dimensions exactly the same orsubstantially similar to a standard MicroSD card. The antenna 802wirelessly communicates with, for example, retail terminals (e.g., POS114) using RF signals. In addition, the transaction card 112 may includean SD interface 808 for physically interfacing a device (e.g., mobiledevice 110). The member 804 may include an arcuate outer surface and/ora substantially flat surface that abuts a portion of the housing 806. Asillustrated in FIG. 8C, the antenna 802 may include a core 810 thatsubstantially defines a length and a width of a three-dimensional shapeof the antenna 802. The core 810 may reflect at least some wirelesssignals to substantially isolate the magnetic field from the transactioncard 112, the mobile device 110, battery elements, and/or other elementsproximate the antenna 802 in such a way that the magnetic field isconcentrated in a direction substantially pointing outside the hostdevice. In some implementations, the core 810 may include a cylindricalferrite core around which the antenna 802 of the transaction card 112 iswrapped. In some implementations, the core 810 may substantially reflectsignals away from the transaction card circuitry, mobile device 110,battery elements, and/or other elements that may be proximate to thetransaction card 112 in such a way that the magnetic field isconcentrated in a direction substantially pointing away from the hostdevice. The antenna 802 may include a width in a range of 9 mm and alength in a range of 14 mm. The resilient member 804 may be rubber,foam, and/or other flexible material. As illustrated in FIG. 8B, theantenna 802 is connected to a transaction circuit 810 (e.g., acontactless chipset) using, for example, a tuning circuit that tunes theantenna 802 to one or more frequencies. The one or more frequencies maybe based, at least in part, on the terminal and/or type of terminal(e.g., POS 114). For example, the tuning circuit may tune the antenna702 to 13.56 MHz for ISO 14443 related transactions. The transactioncard 112 may include an amplifier circuit 812 to amplify (e.g., a factorof 10) signals generated by the antenna 802. In some implementations,the amplifier 812 may be of two types. For example, the amplifier 812may be a passive amplifier that uses passive circuitry to amplify the RFsignals received by the antenna (see FIGS. 13A and 13B) and/or a poweredactive amplifier that uses the energy from the battery of the hostdevice to operate the transaction circuit (see FIG. 14A and FIG. 14B).In some implementations, the transaction card 112 may contain twoadditional RF interface pins 814 a and 814 b to allow the transactioncard to use an external antenna, for example, an antenna contained in aseparate housing for transactions and/or personalization.

FIGS. 9A-9D illustrate an example transaction card 112 an antennaelement 902 and a card element 904. In the illustrated implementations,the card element 904 can be inserted into the antenna element 902 toform the transaction card 112. The antenna element 902 may include anantenna 906 enclosed in a resilient member 908 as illustrated in FIG. 9Band include antenna connections 910 for connecting the antenna 906 tothe card element 904. The card element 904 may include card connections916 corresponding to the antenna connections 910 that connect to, forexample, the contactless chipset. By selectively positioning the antennaelement 902 and the card element 904, the antenna connections 910 mayabut the card connections 916 to form an electrical connection betweenthe two elements. In addition to an electric connection, this connectionmay also provide a mechanical lock between the antenna element 902 andthe card element. Once attached, the contactless chipset may beconnected to the antenna 906 using a tuning circuit that tunes theantenna 906 to one or more frequencies for wireless communicating with,for example, the retail terminal 114. For example, the tuning circuitmay tune the antenna 906 to 13.56 MHz for ISO 14443 relatedtransactions.

In some implementations, the card element 904 can include a width and athickness the same or substantially the same as a standard MicroSD cardsuch that at least a portion of the card element 904 may be insertedinto a standard MicroSD slot. In some instances, the card element 904may be 3-5 mm longer than a standard MicroSD card. The card element 904may include a head protrusion that is slightly wider and/or thicker thana main body of the card element 904. The antenna element 902 typicallyextends outside of the MicroSD slot after insertion of the card element904. In some implementations, the antenna element 902 may include arounded curvature facing away from the slot during insertion and a flatsurface on the other side. In some implementations, the antenna element902 may form an opening having a width approximately 1-2 mm wide. Thewidth of the opening may be approximately equal to the thickness of themain body of the card element 904. In some implementations, the width ofthe opening may match the thickness of the head protrusion of the cardelement 904. In the protrusion example, the thinner side of the cardelement 904 may be initially inserted into the antenna element 902. Insome implementations, the head protrusion of the card element 904 afterinsertion may be substantially flush with the opening. In this instance,the antenna element 902 and the card element 904 may form a cap withflat ends connected by a curvature. The antenna element 902 may be softrubber, foam, and/or other material that may conform to portions of anSD slot during insertion of the card element 904. The antenna 906 may bea flexible PCB including a thin copper antenna coil that is etchedand/or mounted to form the antenna 906. In some implementations, thecard element 904 may include a notch 914 for receiving a portion of theantenna element 902 such as the protrusion 912. In this case, the notch914 and the protrusion 912 may substantially secure the card element 904in the antenna element 902.

FIGS. 10A and 10B illustrates another implementation of the transactioncard 112. In the illustrated implementation, the transaction card 112includes an antenna element 1002 connected to a card element 1004. Thecard element 1004 may include the same or substantially the samedimensions as a standard MicroSD card such that the card element 1004may be inserted into an SD slot. The antenna element 1002 may beattached to a surface of, for example, a mobile device 110. In theillustrated element, the antenna element 1002 includes a base 1005affixed to a surface and configured to receive a pad 107. For example,the base 1005 may be configured to secure the pad 107 adjacent a surfaceof the mobile device 110 as illustrated in FIG. 10B. In someimplementations, the base 1005 may include an adhesive plastic baseincluding a detachable perforation 1006. The pad 1007 may extend arounda mobile device and attaches to the base 1005. In some examples, thebase 1005 and the pad 1007 may form a thin and flat sticker on thesurface of the phone. The pad 1007 may include an antenna 1003, anon-adhesive pad 1008, and/or peripherals elements 1010. The outsideportion of the pad 1007 may include a plastic inlay enclosing theantenna 1003 of the transaction card 112. The antenna 1003 may includecopper coils etched on a very thin plastic film forming one of thelayers of the inlay. The antenna 1003 may be connected to thecontactless chipset of the card element 1004 using a connector 1012(e.g., a flexible thin film) that wraps around the edge of the mobiledevice 110. The connector 1012 may connect the antenna 1003 to thecontactless chipset using a tuning circuit that tunes the antenna 1003to one or more frequencies compatible with, for example, the retailterminal 114. For example, the tuning circuit may tune the antenna 1003to 13.56 MHz for ISO 14443 related transactions. The base 1005 mayinclude a ferrite material that substantially isolates RF analog signalsand the magnetic field from the mobile device 110 (e.g., circuits,battery) in which case the connector may include additional connectivitywires than those used for antenna connection only. The pad 1007 may alsocontain another peripheral 1010 such as a fingerprint scanner connectedto a corresponding logical element in the card element 1004 using thesame connector 1014.

FIGS. 1A and 1B illustrate an example transaction card 112 including awireless connection between an antenna element 1102 and a card element1104. For example, the antenna element 1102 and the card element 1104may include a wireless connection such as Bluetooth. The card element1104 may include the same shape and dimensions as a standard MicroSDcard such that the card element 1104 is substantially in an SD slotduring insertion. The antenna element 1102 may be affixed to a surfaceof a device housing the card element 1104. In some implementations, theantenna element 1102 can form a thin and flat sticker on the surface ofthe mobile device 110 as illustrated in FIG. 11B. The antenna element1102 may include a plastic inlay enclosing at least a portion of theantenna 1104. The antenna 1104 may include a copper coil etched on avery thin plastic film forming one or more layers of the inlay. Theantenna 1104 may connect to the card element 1104 (e.g., the contactlesschipset) using a wireless pairing connection 1113 between a transceiverchip 1114 in the card element 1114 and a corresponding transceiver chip1108 in the antenna element 1108. The wireless connection 1113 mayconnect the antenna 1104 to the card element 1104 using a tuning circuitthat tunes the antenna 1104 to one or more frequencies compatible with,for example, the retail terminal 114. The wireless pairing connectionused in this case may be in the high frequency spectrum (e.g., 900 Mhz,2.4 GHz), which are unlicensed and free for use by domestic appliances,for example. For example, the tuning circuit may tune the antenna 1104to 13.56 MHz for ISO 14443 related transactions. The antenna element1102 may include a ferrite material that reflects wireless signals tosubstantially prevent interference with the mobile device 1110. Theantenna element 1102 may also contain another peripheral 1110 such as afingerprint scanner wirelessly connected to a corresponding logicalelement in the card element using the same wireless connection 1113.

FIGS. 12A and 12B illustrate example transaction cards 112 using acircuit board 1202 of a mobile device to receive and transmit wirelessRF signals. Referring to FIG. 12A, the transaction card 112 includes aplurality of connections 1210 to the circuit board 1202 to interface themobile device 110. Typically, the circuit board 1202 includesinterconnecting copper wires that communicate digital signals. In someimplementations, the circuit board 1202 may communicate analog signalsin addition to the digital signals such as RF signals. In theseinstances, the transaction card 112 may include a frequency filtercircuit 1206 to filter out RF signals (e.g., 13.56 MHz) transmitted by aretail terminal and received by the circuit board 1202. In addition toreceiving RF signals, the transaction card 112 may communicate an analogRF signal to the circuit board 1202 to transmit RF signals to the retailterminal. In some implementations, the transaction card 112 may containtwo additional RF interface pins 1212 a and 1212 b to allow thetransaction card to use an external antenna, for example, an antennacontained in a separate housing for personalization and/or transaction.

Referring to FIG. 12B, the circuit board 1202 includes an externalantenna 1214 that may be used by the transaction card 112. In this case,the original SD interface PINs 1210 may be used for the sole purpose ofstandard SD host communication. The external antenna 1214 may beembedded in, affixed to or otherwise included on the board 1202. Theexternal antenna 1214 are connected to the pins 1216 a and 1216 b on thecircuit board 1202 such that when the transaction card 112 is insertedinto the mobile device the card 112 is connected to the external antenna1214. In some implementations, the pins 1212 a and pins 1212 b canconnect to two the pins 1216 a and 1216 b on the handset circuit board1202, which are in turn connected to the antenna 1214 tuned to receivereader signals. The pins 1216 are positioned on the handset board 1202such that upon insertion of, for example, the MicroSD in the phone, 1212a connects to 1216 a and 1212 b connects to 1216 b. In theseimplementations, the transaction card 112 can exchange RF signals withthe reader using the handset antenna 1214 and the pins 1212 and 1216.

FIGS. 13A and 13B illustrate cross sectional views 1800 a and 1800 b,respectively, of card systems 1302 a and 1302 b that passively amplifyRF signals. In general, passive in this context means amplifyingreceived RF signals without power, electricity, and/or moving parts. Anactive device would thus use power, electricity, or moving parts toperform work. As illustrated, the card system 1302 includes atransaction card 112 and a card element 1303 a. The transaction card 112may be inserted into an opening formed by the card element 1303. Asillustrated, the card is inserted into a side of the card element 1303.Though, the card element 1303 may form other opening without departingfrom the scope of the disclosure such as an opening in the top surface.Both implementations of the card element 1303 include an antenna 1306connected to an SD pin connector 1307. In these instances, thetransaction card 112 connects to the antenna 1306 using the SD pinconnector 1307. Each card system 1302 includes a passive amplificationmodule 1304 that amplifies received RF signals using passive components.For example, the passive amplification module 1304 may include one ormore diodes, one or more resistors, one or more capacitors, and/or othercomponents to passively amplify received RF signals (e.g., a singlediode). Each transaction card includes a transaction circuit 1308 and anassociated virtual ground 1310. The antenna 1306 is connected to thetransaction circuit 1308 through the SD pin connector 1307 and passesreceived RF signals to the transaction circuit 1308. The passiveamplification module 1304 connects to both a lead of the antenna 1306and the virtual ground 1310 of the RF front end 1308. More specificallyand for example, the antenna lead to which the passive amplificationmodule 1304 connects to, is the lead that carries the modulation signalsfor data transfer. As previously mentioned, the passive amplificationmodule 1304 amplifies received RF signals. For example, the passiveamplification module 1304 may amplify the signal by a factor of about10.

Referring to FIG. 13A, the transaction card 112 may include the passiveamplification module 1304 a and connect to the lead of the antenna 1306within the housing of the card 112. In these implementations, the cardelement 1303 may only include the SD pin connector 1307 and the antenna1306. Referring to FIG. 13B, the passive amplification module 1304 bresides in the card element 1303. In these implementations, thetransaction card 112 may include an additional pin 1312 that connectorsto the virtual ground 1310 b when the card 112 is inserted in the cardelement 1303 b. In other words, the card element 1303 may house,enclose, or otherwise include the passive amplification module 1304 b,the SD pin connector 1307 b, and the antenna 1306 b.

Referring 13C, the profile 1320 illustrates a side view of the cardsystem 1302. In the illustrated implementation, the card system 1302include a first portion 1324 with a first thickness indicated by th₁ anda second portion 1326 with a second thickness indicated by th₂. In someimplementations, the first thickness may be approximately a width of acredit card such as, for example, 0.76 mm and/or other widths thatcomply with standards such as ISO 7810, ID1 and CR80. In someimplementations, the second thickness may be at least a thickness of anSD card such as, for example, between about 1 mm and 2.1 mm. Inaddition, the card system 1302 includes a first width (w₁) indicating awidth of the card element 1303, a second width (w₂) indicating a widthof the second portion 1326, and a third width (w₃) indicating a widthassociated a portion 1324 used during the personalization process. Insome implementations, the first width may be approximately the samewidth as a standard credit card in accordance with ISO/IEC 7810standard. In some implementations, the second width may be at least awidth of a microSD card such as, for example, about 11 mm, 20 mm, or 24mm. The third width may be sufficient to personalize the transactioncard 112 using standard personalization machines when inserted into thecard element 1303. In some implementations, the third width may besufficient to receive a mag stripe such as about 9.52 mm. In addition,the third width may be sufficient for graphical personalization such asembossing an account number, name, and expiration date. In theseinstances, the third width may be sufficient to affix a mag stripe, asignature strip, and/or printing characters. In some implementations,the outer edge identified by w₃ may be compatible with currentpersonalization without requiring physical modification.

FIGS. 14A and 14B illustrate cross sections 1400 a and 1400 b of atransaction card 112 that passively amplifies an internal antenna 1402.Referring to FIG. 14A, the card 112 includes a passive amplificationmodule 1406 that amplifies received RF signals using passive components.In the illustrated implementation, the passive amplification module 1406a is a component separate from the transaction circuit 1404 a. Thepassive amplification module 1406 a may include one or more diodes, oneor more resistors, one or more capacitors, and/or other components topassively amplify received RF signals (e.g., a single diode). Thetransaction circuit 1404 includes a virtual ground 1408. The internalantenna 1402 is connected to the transaction circuit 1404 through twodedicated antenna leads and passes received RF signals to thetransaction circuit 1404. The passive amplification module 1406 connectsto both a lead of the internal antenna 1402 and the virtual ground 1408of the transaction circuit 1404. More specifically and for example, theantenna lead to which the passive amplification module 1304 connects tois, the lead that carries the modulation signals for data transfer. Aspreviously mentioned, the passive amplification module 1406 amplifiesreceived RF signals. For example, the passive amplification module 1406may amplify the signal by a factor of about 10. Referring to FIG. 14B,the cross section 1400 b illustrates that the passive amplificationmodule 1406 b is included in the transaction circuit 1408 b. In theseimplementations, the passive amplification module 1406 b connects to thevirtual ground 1408 b and the lead of the antenna 1402 b in thetransaction circuit 1408 b.

In addition, either implementation may operate in a power-off mode. Inother words, the received RF signals may power the transaction card 112independent of external power source (e.g., mobile-phone battery). Insome implementations, the passive amplifier 1406 may draw enough powerfrom the RF signals transmitted by readers to power the smartchip ortransaction circuit 1404. For example, the transaction card 112 may usepower from the RF signals in response to the host device losing power.In some implementations, the transaction circuit 1404 can receive asufficient voltage output from the passive amplifier 1406 to boot up andstart operating. In these instances, the transaction card 112 mayexecute transactions with the reader including responding appropriatelyfor a successful transaction. For example, a user may lose power on ahost device in connection with executing a transit application, thetransaction card 112 may be able to pay for his metro ticket in thepower-off mode. The transaction card 112 may power the transactioncircuit using received RF signals.

FIGS. 15A and 15B illustrate cross sections 1500 a and 1500 b oftransaction cards 112 that actively amplify RF signals. For example, thetransaction card 112 amplifies signals using an external power supply(e.g., mobile-phone battery). Each transaction card 112 includes anactive amplification module 1502. The output of the passiveamplification module is connected to either the lead of the antenna 1504or to a dedicated PIN 1503 in the transaction circuit. For example, theoutput of the amplification module 1502 connects to the non modulatinglead of the antenna 1504. The input to the amplification module 1502 isregulated voltage supplied from the microcontroller unit 1501 of thetransaction card which in turn receives power from the host devicethrough the voltage output PIN 1506 of the SD interface. The pin 1506may be a standard microSD pin (see FIG. 15A) and/or a dedicated pin (seeFIG. 15B). In connection with inserting the card 112 in a host device,the pin 1506 connects the active amplification module 1502 to anexternal power source 1508 through the MCU 1501 of the transaction card.For example, the external power sources 1508 may be a battery of thehost device. The active amplification module 1502 uses power from theexternal power source 1508 to amplify signals received and/ortransmitted by the antenna 1504. In some implementations, the activeamplification module 1502 can amplify signals a factor of about 10.

FIGS. 16A-C illustrate views 1600 a-c of transaction circuits 1602 a-cof a transaction card in accordance with some implementations of thepresent disclosure. In particular, the transaction circuit 1602 includesa printed circuit board (PCB) antenna 1604. In these implementations,the PCB antenna 1604 is embedded (or printed) with metal traces (e.g.,copper) in a circuit board. For example, the antenna 1604 b may beembedded in the main MicroSD circuit board 1602, where the rest of theIn2 Pay hardware components are mounted. For example, the antenna 1604 bmay also be partly embedded in the main MicroSD circuit board 1602 andmay partly be in a separate antenna only PCB board. Two implementationsinclude: (1) embed the entire antenna metal traces into the circuitboard (see FIG. 16B); and (2) attach a separate antenna-only PCB ontothe main MicroSD circuit board 1602 (see FIG. 16C). The antenna tracesmay be multi-layered such as regular multi-layer signal traces in anormal circuit board. In these implementations, the layers are connectedthrough metal vias such as with regular multi-layer signal traces.

In some implementations, the PCB antenna 1604 can be manufactured usingstandard MicroSD manufacturing (assembly) flow and techniques such asmetal trace lithography and planar processing, component pick-and-place,and/or component attachment. As a result, the PCB antenna 1604 may bebetter suited for automated mass manufacturing. In addition, metaltraces can be fairly compact, i.e., space saving, as compared withcoiled antennas. For example, more turns and longer wires may be used inmetal traces in the PCB antenna 1604 as compared with coiled antennas.

In some implementations after the metal traces are manufactured aroundthe periphery of the PCB antenna, it might leave available a cylindricalempty space that could be hollow. This hollow cylindrical space may beused to situate a ferrite core that may be used to magnetically attractthe RF field available from the terminal and increase the performance ofthe antenna system.

FIG. 17 illustrates a cross section 1700 of a transaction card 112 thatactively amplifies RF signals. For example, the transaction card 112amplifies signals using an external power supply such as a battery in amobile device. In the illustrated implementation, the transaction card112 includes a transceiver 1702, a modulator 1704, and an amplifier thatactively communicate RF signals. The transceiver 1702 wirelesslytransmits and receives RF signals to and from transaction terminals. Insome implementations, the transceiver 1702 may be a chip antenna thatbeams signals in a configurable frequency range. The modulator 1704 isconnected to the transceiver 1702 and modulates the signal in accordancewith one or more standards. For example, the modulator 1704 may be asoftware modulator that modulates the frequency range to the 13.54 MHzrange. For example, the software code that drives the software modulatorto operate in the appropriate frequency may reside in theMicroController Unit 1701 of the transaction card. In connection withinserting the card 112 in a host device, the power amplifier 1706connects to the a regulated output voltage supplied by the MCU 1701which in turn receives power from an external power source and thetransceiver 1702. For example, the external power sources may be abattery of a mobile host device. The power amplifier 1706 uses powerfrom the external power source to amplify signals received and/ortransmitted. In some implementations, the power amplifier 1706 canamplify signals a factor of about 10. The power amplifier 1706 mayensures that the amplitude and voltage delivered to the smartchip isproperly set to ensure operation.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention.Accordingly, other embodiments are within the scope of the followingclaims.

1. A transaction card, comprising: a first interface that connects to amicroSD slot of a mobile host device; a second interface that includesan internal antenna for wirelessly communicating with retail terminals;secure memory that stores user credentials and a payment applicationused to execute financial transactions with the retail terminals, theuser credentials and the payment application associated with a financialinstitution; a user-interface module that presents and receivesinformation through a Graphical User Interface (GUI) of the mobile hostdevice; a transaction processing module that executes the paymentapplication using the user credentials in response to at least atransaction request received by the RF module and transmits at least onetransaction response to the retail terminal based, at least in part, onthe executed payment application; and an amplification module configuredto amplify at least received RF signals.
 2. The transaction card ofclaim 1, further comprising the transaction processing module includinga virtual ground, the amplification module connected to both the lead ofthe antenna and the virtual ground of the transaction processing module.3. The transaction card of claim 1, the amplification module operatesindependent of the transaction processing module and includes onlypassive components.
 4. The transaction card of claim 3, the passivecomponents including at least one of one or more diodes, one or moreresistors, or one or more capacitors.
 5. The transaction card of claim1, the amplification module provides at least one of voltageamplification or signal amplification to the card based on received RFsignals and independent of a battery.
 6. The transaction card of claim1, the amplification module is built into the transaction processingmodule
 7. The transaction card of claim 1, further comprising internalcircuitry that powers the amplification module and the transactionprocessing modules during insertion in the transaction card and whilethe device is powered on.
 8. The transaction card of claim 1, whereinthe amplification module enables the transaction card to operate betweena reading range of about 0.1 to about 10 cm.
 9. The transaction card ofclaim 1, further comprising at least two pins configured to connect toan external antenna.
 10. The transaction card of claim 9, the externalantenna including at least one of an external antenna in a credit-cardshaped element configured to receive the transaction card or an externalantenna included in a mobile host device.
 11. The transaction card ofclaim 1, further comprising: a ninth and tenth pin configured to connectwith an external antenna in a mobile host device; and a multiplexerconfigured to switch between the card using the internal antenna and theexternal antenna.
 12. The transaction card of claim 1, furthercomprising a housing that encloses at least a portion of the securememory, the user-interface module the processing module, and theamplification module.
 13. The transaction card of claim 12, wherein thehousing includes a substantially-planar interior surface, the antennaincludes a coiled antenna adjacent the substantially-planar interiorsurface.
 14. The transaction card of claim 12, wherein the internalantenna includes a helical antenna, the housing enclosing the helicalantenna.
 15. The transaction card of claim 14, further comprising adielectric core, wherein the helical antenna is adjacent a surface ofthe dielectric core.
 16. The transaction card of claim 15, wherein thedielectric core at least includes ferrite.
 17. The transaction card ofclaim 12, wherein the housing includes an external surface, furthercomprising a resilient element substantially encasing the antenna andabutting the external surface of the housing.
 18. The transaction cardof claim 17, wherein the antenna includes a coiled antenna.
 19. Thetransaction card of claim 17, wherein the antenna includes a helicalantenna.
 20. The transaction card of claim 19, further comprising adielectric core, wherein the helical antenna is adjacent a surface ofthe dielectric core.
 21. The transaction card of claim 20, wherein thedielectric core at least includes ferrite.
 22. The transaction card ofclaim 1, further comprising an isolation element that substantiallydirects interference signals generated by the microSD payment card awayfrom circuitry of the mobile host device.
 23. The transaction card ofclaim 1, the isolation element including ferrite.
 24. The transactioncard of claim 22, wherein the isolation element substantially preventsan additional load on a battery of the mobile host device resulting fromthe interference signals.
 25. The transaction card of claim 1, theinternal antenna comprising a Printed Circuit Board (PCB) antenna.